Maybe reuse FreshNameCreator from the compiler?

It would have a global indexing which would make any debugging harder as it would keep undesired state from one macro expansion to the other.

If a macro contains many usage of let, then it faces the same problem.

FreshNameCreator is better in the sense that it keeps different counters for different names, instead of using one global counter.

But it uses a global counter across all files in the compilation run and each macro expansion site which is what we are trying to avoid.

It's possible to call def setFreshNames(freshNames: FreshNameCreator) on Context before macro expansion.

Maybe a could try to create a fresh FreshNameCreator for each macro expansion site.